Where is that input coming from? Something in your grammar itself? Can you give me an example? I am not saying this isn't a good idea, but I have forgotten where the type map comes in to it to be honest?

Also, is there a reason for you to do force pushes? Just forgot the -s on the commit?

Here's some examples: https://github.com/ethereum/solidity/blob/c6aab84a0c25a9348e22326f12c2ebbf407989dc/docs/grammar/SolidityParser.g4#L161-L164 (see the PR linked to this one for context). Also related: ethereum/solidity#9679, which is relevant to the C++ codegen.

Reason for force-pushing is to keep the commit history clean (there was a small typo in the original commit i pushed that the CI flagged) (and yes, didn't realize the -s was a requirement for this repo).

Here's some examples: https://github.com/ethereum/solidity/blob/c6aab84a0c25a9348e22326f12c2ebbf407989dc/docs/grammar/SolidityParser.g4#L161-L164 (see the PR linked to this one for context). Also related: ethereum/solidity#9679, which is relevant to the C++ codegen.

Reason for force-pushing is to keep the commit history clean (there was a small typo in the original commit i pushed that the CI flagged) (and yes, didn't realize the -s was a requirement for this repo).

Ah, I see. I thought it was about embedded code in the parser. On the face of it, this does not seem unreasonable. Let me check your changes...

@parrt This can be merged